| Avoid slowing down the critical rendering path (avoidRenderBlocking) | The page has 14 blocking requests and 8 in body parser blocking (9 JavaScript and 13 CSS). | 10 |
| Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path. |
| Offenders: http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/js/v...s/v4-shims.min.js http://192.168.100.104/wp-content/themes/astra/assets/js/minified/frontend.min.js?ver=4.0.2 http://192.168.100.104/wp-content/plugins/elementor/assets/js/webpack.runtime.min.js?ver=3.11.1 http://192.168.100.104/wp-includes/js/jquery/jquery.min.js?ver=3.6.1 http://192.168.100.104/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2 http://192.168.100.104/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.11.1 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/waypoints/waypoints.min.js?ver=4.0.2 http://192.168.100.104/wp-includes/js/jquery/ui/core.min.js?ver=1.13.2 http://192.168.100.104/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.11.1 http://192.168.100.104/wp-content/uploads/elementor/css/post-4.css?ver=1676664428 http://192.168.100.104/wp-content/uploads/omgf/google-fonts-1/google-fonts-1.css?ver=1676664295 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...ntawesome.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...css/solid.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/js/v...s/v4-shims.min.js |
| Don't scale images in the browser (avoidScalingImages) | The page has 1 image that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them. | 90 |
| Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one. |
| Offenders: http://192.168.100.104/wp-content/uploads/2018/11/quote-1.png |
| Inline CSS for faster first render (inlineCss) | The page has both inline styles as well as it is requesting 13 CSS files inside of the head. Let's only inline CSS for really fast render. | 90 |
| Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded. |
| Offenders: http://192.168.100.104/wp-content/themes/astra/assets/css/minified/frontend.min.css?ver=4.0.2 http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/astra-google-f...-google-fonts.css http://192.168.100.104/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/eicons/css/elemen...tor-icons.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/css/frontend-lite.min.css?ver=3.11.1 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/swiper/v8/css/swi...ss/swiper.min.css http://192.168.100.104/wp-content/uploads/elementor/css/post-442.css?ver=1676660369 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...e/css/all.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/.../v4-shims.min.css http://192.168.100.104/wp-content/uploads/elementor/css/post-4.css?ver=1676664428 http://192.168.100.104/wp-content/uploads/omgf/google-fonts-1/google-fonts-1.css?ver=1676664295 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...ntawesome.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...css/solid.min.css |
| Avoid CPU Long Tasks (longTasks) | The page has 1 CPU long task with the total of 52 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 52 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks. | 80 |
| Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler. |
| Offenders: unknown |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 39 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 2.2 MB the next access. | 0 |
| Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request. |
| Offenders: http://192.168.100.104/wp-content/themes/astra/assets/css/minified/frontend.min.css?ver=4.0.2 http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/astra-google-f...-google-fonts.css http://192.168.100.104/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/eicons/css/elemen...tor-icons.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/css/frontend-lite.min.css?ver=3.11.1 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/swiper/v8/css/swi...ss/swiper.min.css http://192.168.100.104/wp-content/uploads/elementor/css/post-442.css?ver=1676660369 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...e/css/all.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/.../v4-shims.min.css http://192.168.100.104/wp-content/uploads/elementor/css/post-4.css?ver=1676664428 http://192.168.100.104/wp-content/uploads/omgf/google-fonts-1/google-fonts-1.css?ver=1676664295 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...ntawesome.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/...css/solid.min.css http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/js/v...s/v4-shims.min.js http://192.168.100.104/wp-content/themes/astra/assets/js/minified/frontend.min.js?ver=4.0.2 http://192.168.100.104/wp-content/plugins/elementor/assets/js/webpack.runtime.min.js?ver=3.11.1 http://192.168.100.104/wp-includes/js/jquery/jquery.min.js?ver=3.6.1 http://192.168.100.104/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.3.2 http://192.168.100.104/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.11.1 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/waypoints/waypoints.min.js?ver=4.0.2 http://192.168.100.104/wp-includes/js/jquery/ui/core.min.js?ver=1.13.2 http://192.168.100.104/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.11.1 http://192.168.100.104/wp-content/uploads/2018/11/quote-1.png http://192.168.100.104/wp-content/uploads/2020/01/hiking-v1.jpg http://192.168.100.104/wp-content/uploads/2020/01/walking-v1.jpg http://192.168.100.104/wp-content/uploads/2021/02/outdoor-image-01.jpg http://192.168.100.104/wp-content/uploads/2021/02/outdoor-image-03.jpg http://192.168.100.104/wp-content/uploads/2018/11/winter-sport.jpg http://192.168.100.104/wp-content/uploads/2018/11/water-sports-04.jpg http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/lato-normal-latin-400.woff2 http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/poppins-normal-latin-700.woff2 http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/lato-normal-latin-700.woff2 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/webf...a-solid-900.woff2 http://192.168.100.104/wp-content/uploads/2018/11/hero-bg.jpg http://192.168.100.104/wp-content/uploads/2021/02/outdoor-image-04.jpg http://192.168.100.104/wp-content/uploads/2018/11/camp-1.jpg http://192.168.100.104/wp-content/uploads/2020/01/section-bg-img.jpg http://192.168.100.104//wp-content/plugins/elementor/assets/js/text-editor.2c35a...950.bundle.min.js http://192.168.100.104/favicon.ico |
| Total CSS size shouldn't be too big (cssSize) | The total CSS transfer size is 87.8 kB and uncompressed size is 442.5 kB. That is big and the CSS could most probably be smaller. | 50 |
| Description: Delivering a massive amount of CSS to the browser is not the best thing you can do, because it means more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page. And make sure to remove CSS rules when they aren't used anymore. |
| Offenders: |
| Avoid too many fonts (fewFonts) | The page has 4 font requests. Do you really need them? What value does the fonts give the user? | 60 |
| Description: How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive. |
| Offenders: http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/lato-normal-latin-400.woff2 http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/poppins-normal-latin-700.woff2 http://192.168.100.104/wp-content/uploads/omgf/astra-google-fonts/lato-normal-latin-700.woff2 http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/webf...a-solid-900.woff2 |
| Total image size shouldn't be too big (imageSize) | The page total image size is 1.9 MB. It's really big. Is the page using the right format for the images? Can they be lazy loaded? Are they compressed as good as they can be? Make them smaller by using https://imageoptim.com/. | 50 |
| Description: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user. |
| Make each CSS response small (optimalCssSize) | http://192.168.100.104/wp-includes/css/dist/block-library/style.min.css?ver=6.1.1 size is 15.5 kB (15493) and that is bigger than the limit of 14.5 kB. http://192.168.100.104/wp-content/plugins/elementor/assets/lib/font-awesome/css/all.min.css?ver=3.11.1 size is 14.7 kB (14659) and that is bigger than the limit of 14.5 kB. Try to make the CSS files fit into 14.5 KB. | 80 |
| Description: Make CSS responses small to fit into the magic number TCP window size of 14.5 KB. The browser can then download the CSS faster and that will make the page start rendering earlier. |
| Offenders: |
| Total page size shouldn't be too big (pageSize) | The page total transfer size is 2.3 MB, which is more than the coach limit of 2 MB. That is really big and you need to make it smaller. | 0 |
| Description: Avoid having pages that have a transfer size over the wire of more than 2 MB (desktop) and 1 MB (mobile) because that is really big and will hurt performance and will make the page expensive for the user if she/he pays for the bandwidth. |
| Offenders: |
| Avoid missing and error requests (responseOk) | The page has 1 error response. The page has 1 response with code 404. | 90 |
| Description: Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it. |
| Offenders: http://192.168.100.104/favicon.ico |
